fix: align LinkedIn publish Telegram notification with other formats - #200
Merged
Conversation
Replaces the raw urn:li:share:... URN and em-dash separator with the same bold-repo + bullet + link style used by the PR/issue/release notifications, via a dedicated prepare-telegram-linkedin-message action (mirroring prepare-telegram-release-message). The success message now links to the actual LinkedIn post instead of showing its opaque URN. Also fixes unescaped MarkdownV2 special characters (e.g. "." in tags, "-" in repo names) that would have broken the message under parse-mode: MarkdownV2 if built inline in the workflow YAML. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
—-separated plain text (showing the rawurn:li:share:...) with the same*repo* • [link](url) ...style used by PR/issue/release Telegram notifications.prepare-telegram-linkedin-message, mirroringprepare-telegram-release-message's prepare/send split, with proper MarkdownV2 escaping — the previous inline YAML message would have broken underparse-mode: MarkdownV2on tags/repos containing.or-.https://www.linkedin.com/feed/update/{urn}/) instead of showing the opaque URN.Test plan
python3 -m pytest test/hooks/actionlint.sh .github/workflows/publish-linkedin-release-shared.ymlyamllint -c config/yamllint.yml .github/workflows/publish-linkedin-release-shared.yml .github/actions/prepare-telegram-linkedin-message/action.yml